 (Disk 1).iso/pc/technical documentation/macintosh technotes and q&as/technotes/tn/acrobat.gif) Acrobat file (84K) |
 (Disk 1).iso/pc/technical documentation/macintosh technotes and q&as/technotes/tn/clarisworks.gif) ClarisWorks 4 file (36K) |
 (Disk 1).iso/pc/technical documentation/macintosh technotes and q&as/technotes/tn/quickview.gif) QuickView file (473K) |
|
Acrobat file (84K) |
ClarisWorks 4 file (36K) |
QuickView file (473K) |
| Technote 1003 | OCTOBER 1995 |
This Note highlights two points - interrupt latency, and task record
ownership - that might be unclear after reading the chapter
"Deferred Task Manager" in Inside Macintosh:Processes.
This Note is intended for all developers who need to install a lengthy
interrupt task capable of running with all interrupts enabled.
Contents
DTInstall and when that task is performed. This
time is not deterministic and cannot be controlled. Real-time response
cannot be guaranteed on Macintosh computers with or without the use of
deferred tasks.DTInstall, you are
giving your DeferredTask record to the system; the system
owns the record until the routine designated by the
DeferredTask record's dtAddr field is entered.
During the time the system owns a DeferredTask record, you
must not change any of the fields of that record.
Similarly, you must not depend on the contents of the record when it is
owned by the system. The system is free to alter the record in any
fashion while it has ownership and restores the record to its original
state prior to invoking the deferred task. You must not install a
DeferredTask record which is already owned by the system.
Finally, you must not use the dtReserved field for any purpose; it
should be set to zero prior to installing a deferred task with
DTInstall.
The references section has been updated. Information found in the
chapter "Deferred Task Manager" in Inside
Macintosh:Processes, has been deleted.